On-demand rental of electric vehicles

ABSTRACT

An indication that a ride associated with an electric vehicle has ended is received. An availability state of the electric vehicle is determined based at least on a current battery charge level of the electric vehicle and a dynamic charge threshold. Information reflecting the availability state of the electric vehicle in a set of geographic location and availability state information of vehicles comprising a fleet of electric vehicles available to be displayed is included via a user interface based at least in part on the respective availability state of the respective electric vehicles comprising the fleet of electric vehicles.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/382,725 entitled ON-DEMAND RENTAL OF ELECTRIC VEHICLES filed Apr. 12, 2019 which is incorporated herein by reference for all purposes, which claims priority to U.S. Provisional Patent Application No. 62/658,069 entitled ON-DEMAND RENTAL OF ELECTRIC VEHICLES filed Apr. 16, 2018 which is incorporated herein by reference for all purposes, and claims priority to U.S. Provisional Patent Application No. 62/668,070 entitled CROWDSOURCING VIRTUAL DOCKS AS PART OF A VEHICLE-SHARING SYSTEM filed May 7, 2018 which is incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

On-demand vehicle-sharing provides consumers with the ability to rent vehicles instantly through a mobile device. Traditionally, human-powered vehicles such as bicycles have been the primary vehicle of choice for these vehicle-sharing programs. However, consumers may want to have access to shared use of electric vehicles as well.

The sharing of electric vehicles poses unique challenges when compared to sharing non-electric vehicles. For example, needing to charge vehicle batteries is an obstacle that must be overcome to have a successful electric vehicle-sharing program. In addition, on-demand vehicles not tied to a particular docking location may be left by a user at a sub-optimal or not authorized location. Further, on demand electric vehicles may become damaged and need repairs or other maintenance.

Fixed docking stations with vehicle charging capabilities could in theory be used to charge electric vehicles when not in use. However, docking stations are not ideal for vehicle-sharing models as they drastically restrict the number of locations users can pick up vehicles from, and special docking station and/or vehicle equipment, such as chargers, connectors, and power sources, would be required and could provide a disincentive to use, especially if the docking or undocking were made less convenient or more difficult for the user.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1A is a block diagram illustrating aspects of an embodiment of a system to rent electric vehicles for use “on demand”.

FIG. 1B is a block diagram illustrating an embodiment of a system to rent electric vehicles for use “on demand”.

FIG. 1C is a state diagram illustrating states in which each on demand electric vehicle comprising a fleet may be, and transitions between such states, in an embodiment of a system to perform crowdsourced charging of on-demand electric vehicles.

FIG. 2A is a flow chart illustrating an embodiment of a process to provide the ability to rent electric vehicles rental on demand.

FIG. 2B is a flow chart illustrating an embodiment of a process to provide via a user interface information to enable a user to find electric vehicles available for rental on demand.

FIG. 2C is a flow chart illustrating an embodiment of a process to provide via a user interface information and functionality to use an electric vehicle available for rental.

FIG. 3A is a diagram illustrating an embodiment of a user interface to locate and rent on-demand electric vehicles.

FIG. 3B is a diagram illustrating an embodiment of a user interface to locate and rent on-demand electric vehicles.

FIG. 4 is a diagram illustrating an embodiment of a user interface to rent an on-demand electric vehicle or charge on-demand electric vehicles.

FIG. 5 is a flow chart illustrating an embodiment of a process to receive and process an indication to ride an electric vehicle.

FIG. 6 is a flow chart illustrating an embodiment of a process to perform end-of-ride processing.

FIG. 7 is a diagram illustrating an embodiment of a user interface to provide instructions to properly park a vehicle at a specific location.

FIG. 8A illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8B illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8C illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8D illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8E illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8F illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8G illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

FIG. 8H illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

On-demand shared use of electric vehicles is disclosed. In various embodiments, each of a plurality of electric vehicles comprising a fleet transmits its geo-location data to a cloud server. A mobile app that communicates and controls rudimentary functions of the vehicle is provided. Riders use the mobile app to find and ride vehicles.

In various embodiments, one or more of the following requirements are met to facilitate a fleet of on-demand rentals of electric vehicles.

-   -   1. Vehicle-connectivity to the internet, e.g., direct         connectivity from the vehicle to the internet and/or indirect         connectivity through a user's mobile device;     -   2. A user-interface that can communicate with the vehicles and         control rudimentary aspects of the vehicles;     -   3. A user-interface that can train users on crucial components         of the system such as how to be safe with the vehicles, how to         ride according to local regulations, etc., and     -   4. A crowdsourced system to attract and incentivize people to         “replenish” (i.e. charge, repair, etc.) the vehicles.

In various embodiments, a user-interface can take the form of a mobile application, a smartwatch application, a smart helmet or other wearable technology, or any other interface that communicates digital information to a user and has connectivity, directly or indirectly, to the internet.

In various embodiments, on-demand electric-vehicles are charged and/or otherwise serviced by a crowd-sourced group of independent contractors. In various embodiments, crowdsourced servicing incentives are determined and updated dynamically, via automated processes, and provided to crowdsourced service providers via automatic updates. In some embodiments, a portal for users to sign up to service vehicles is provided. A mobile app that displays vehicle geo-location and dynamically updated pricing or other incentive data is provided. Dynamically determined prices and other incentives to service vehicles are displayed to users, e.g., via the mobile app.

Examples of electric vehicles made available for on demand use as disclosed herein include without limitation electric scooters; electric bikes, minibikes, motor scooters, and motorcycles; skateboards, hover boards, and other single- or multi-wheeled electrically-powered boards; and self-balancing personal electric vehicles.

In various embodiments, the following terms (in bold) and associated meanings may be used to describe embodiments of a system to perform crowdsourced servicing of on-demand electric vehicles as disclosed herein:

Available State. Vehicles in the “Available” state satisfy all conditions for being rentable by a rider, in various embodiments. For example, in some embodiments, a vehicle is designated by the system as “Available” if the vehicle is in good repair and has sufficient charge to be rented, is in a location from which the vehicle is authorized to be rented, and has not been reported as lost, stolen, damaged, etc. In some embodiments, techniques disclosed herein are used to ensure that Available vehicles are not “captured” (e.g., taken out of service for charging, repairs, updates, etc.) by crowdsourced independent contractors. Within the “Available” state, in various embodiments, a given vehicle may be “In Use” by a rider (currently rented and ride not yet ended by the user) or “Free” (not currently rented and otherwise fulfilling the conditions to be “Available” for use).

Unavailable State. In various embodiments, vehicles in the “Unavailable” state violate at least one of the conditions that constitute an “Available” vehicle. In various embodiments, techniques disclosed herein are used to ensure that Unavailable vehicles cannot be rented by a rider.

Servicing State. In various embodiments, vehicles in the “Servicing” state are in the process of being serviced by a crowdsourced independent contractor. In various embodiments, techniques disclosed herein are used to ensure that vehicles in the Servicing State cannot be rented by a rider. In some embodiments, a vehicle in the Servicing State may also and/or instead be considered in a state associated with the particular service being provided, e.g., a “Charging State” for charging and a “Maintenance State” for repairs and/or other maintenance.

Charger. In various embodiments, a “charger” (or “Charger”) is an independent contractor who captures, charges, and deploys vehicles. In various embodiments, they are paid based on the number of vehicles they successfully capture, charge, and/or deploy. In some embodiments, there may be multiple Chargers and/or other workers who contribute to fulfilling the Servicing State.

Mechanic. In various embodiments, a “mechanic” (or “Mechanic”) is an independent contractor who captures, repairs and/or performs other maintenance on, and deploys vehicles. In various embodiments, they are paid based on the number of vehicles they successfully capture, service, and/or deploy. In some embodiments, there may be multiple Mechanics and/or other workers who contribute to fulfilling the Servicing State.

Replenisher. In various embodiments, a “replenisher” (or “Replenisher”) is an independent contractor who captures, performs a service on or with respect to (e.g., charges, repairs, relocates), and/or deploys vehicles. A Replenisher may be a Charger, a Mechanic, or another crowd sources provider of a service or function with respect to on demand electric vehicles.

Capture. In various embodiments, Chargers “capture” vehicles while they are in the Unavailable state. Capture may include one or more of retrieving the vehicle from a location at which it was left by a rider, and taking the vehicle to a charging location or an intermediate location on its way to a charging location.

Hours of Operation. In various embodiments, “Hours of Operation” refer to the time period when vehicles can be rented by a rider.

Operational Boundaries. In various embodiments, “Operational Boundaries” refer to a pre-determined, closed boundary of location coordinates of where vehicles can be rented by a rider.

Deploy. In various embodiments, Chargers “deploy” vehicles once the vehicle is ready to be re-introduced into the Available fleet. Deploying may include delivering a charged vehicle to a location from which it may be rented.

Rider. In various embodiments, “Riders” are the consumers who rent vehicles.

A number of examples described below refer to vehicles being charged by chargers; however, in various embodiments, the same systems, processes, and interfaces are adapted to incentive Replenishers to perform other tasks, such as repair/maintenance and/or vehicle retrieval, delivery, deployment, and/or relocation services.

FIG. 1A is a block diagram illustrating aspects of an embodiment of a system to rent electric vehicles for use “on demand”. In the example shown, the system 100 includes a plurality of electric vehicles available for use on demand, represented in FIG. 1A by electric scooter 102. Electric scooter 102 and other vehicles in the fleet are propelled by an electric motor (not shown) powered by a battery (not shown), e.g. a battery in the foot board and/or located elsewhere in scooter 102. The battery of scooter 102 is depleted through use. Charger equipment 104 plugged into a power outlet or other power source 106 is used to charge the battery of scooter 102.

In various embodiments, independent contractors referred to herein as “chargers”, are recruited via a mobile app or other interface to charge vehicles comprising the fleet, such as scooter 102. Each vehicle is equipped with a circuit board 108 comprising a communication functionality, such as WiFi, Bluetooth, GPS, cellular, etc., enabling the vehicle to connect directly or indirectly (e.g., via a user's mobile device) via the Internet 110 to a backend server 112. The connection may be via direct wireless communication 116, if equipped, or indirect, e.g., via Bluetooth or other near field communication 118 to a user's mobile device 114 configured to relay information via communications 120 to the backend server 112 via the Internet 110. For example, a mobile device 114 carried by a user renting and/or riding the scooter 102, a mobile device 114 carried by a user who passes near the scooter 102 on the street, and/or a mobile device 114 of a user who has retrieved the scooter 102 to charge it may be used to receive vehicle state information from the scooter 102 and relay such information via the Internet 110 to backend server 112.

In various embodiments, vehicle state information including at least a battery charge level of scooter 102 and a location of scooter 102 may be reported from time to time and/or upon occurrence of certain events (e.g., state transitions, as described in connection with FIG. 1B) to backend server 112. Backend server 112 in various embodiments maintains current and/or historical vehicle state information in a vehicle and user data store 122, e.g., a database. Vehicle information stored in data store 122 may include without limitation a history of preventive maintenance, repairs, ride and/or other usage history and data, user and/or charger feedback about the vehicle and/or its condition, charge state, battery health, etc. User information stored in data store 122 may include without limitation records associated with users registered to ride vehicles comprising the fleet, such as scooter 102, and users registered to charge vehicles comprising the fleet in exchange for a payment and/or other consideration (e.g., ride credits, virtual currency, status or other recognition within a user community, etc.). User records for users who charge vehicles (sometimes referred to as “chargers”) in various embodiments may include information indicating which vehicles are currently being charged (or reserved to be charged) by the user; financial account information; past, current, or expected payment information; charger performance metrics, such as percent on time redeployment, etc.; etc.

FIG. 1B is a block diagram illustrating an embodiment of a system to rent electric vehicles for use “on demand”. In the example shown, electric scooter 102 of FIG. 1A is shown to be included in a fleet 120 of electric scooters including scooters 122 deployed throughout a geographic service area.

In various embodiments, each of the scooters 102, 122 is configured to report its geo-location and state information (e.g., charge, other status or health information, etc.) via the internet, either through direct communication by a transceiver built into the scooter 102, 122 or indirectly via near field communications 118 between the scooter 102, 122 and mobile devices that have the associated mobile app installed and running and come within near field communication range of such a mobile device, such as mobile device 114 in the example shown.

In various embodiments, a user of mobile device, such as mobile device 114, receives via an app on the mobile device 114 information to find, unlock, and ride a selected one of the scooters (or other vehicle) 102 122. The mobile app provides a map-based or other user interface to locate vehicles in an area of interest to the user. The corresponding locations are displayed on the map. For example, the default location may be a walkable radius from the geo-location of the mobile device. However, in some embodiments, the user may change the view, such as by zooming in or out, using a drag or other gesture to search for vehicles in another area, a search box to enter a search area or center, etc.

In various embodiments, the mobile app includes functionality to teach the user how to activate and ride the electric vehicle and to do so safely and while complying with local regulations. When a user is done riding, the user indicates the “end” of their ride. In some embodiments, the mobile app may provide general or location-specific instructions as to how and where to park the vehicle. The mobile app may prompt the user to take a photo of the vehicle as parked. In various embodiments, the photo may be stored (e.g., for a prescribed time) to be available for use in checking or verify the condition and placement of the vehicle as left by the user at the end of the user's ride. In some embodiments, machine learning and other techniques are used to detect via automated processing, based on an image of the vehicle as parked, whether the vehicle was parked properly or not.

FIG. 1C is a state diagram illustrating states in which each on demand electric vehicle comprising a fleet may be, and transitions between such states, in an embodiment of a system to perform crowdsourced charging of on-demand electric vehicles.

In the example shown, state machine 140 includes Available State 142. In various embodiments, a vehicle in the Available State 142 is available to be rented by a rider. For example, a vehicle that is fully or adequately charged and in a permitted location (e.g., within applicable Operational Boundaries) during a time in which use is permitted (e.g., within applicable Hours of Operation) may be in the Available State 142. In various embodiments, vehicle in the Available State 142 are visible in a mobile user interface available to riders and may be claimed/reserved for use via the mobile user interface. In some embodiments, state information indicating a vehicle is in the Available State 142 is stored in a backend database, such as vehicle and user data store 122 of FIG. 1A. Vehicle state information (e.g., location, charge level, etc.) reported periodically (on occurrence of a triggering event, opportunistically, etc.) to a backend server, such as backend server 112, is used in various embodiments to determine whether a vehicle is in the Available State 142 and to store in the backend database data representing the state. In some embodiments, a vehicle in the Available State 142 is not subject to being captured by a charger.

In various embodiments, the vehicle constantly monitors itself and its surroundings to determine if it is in violation of any conditions of being in the Available State 142. A non-exhaustive list of primary conditions that qualify a vehicle to be and/or remain in the Available State 142 in various embodiments includes one or more of:

-   -   1. The vehicle's battery levels are sufficiently charged given         current time, location, and other contextual factors     -   2. The vehicle's geo-location is inside the operational         boundaries     -   3. The current time-of-day is inside the hours of operation

In some embodiments, one or more other conditions that relate to the vehicle operating status, weather conditions, or other factors, must be satisfied for a vehicle to be considered to be in the Available State 142.

In some embodiments, the threshold for what constitutes as “sufficiently charged” to remain in the Available State 142 may change dynamically throughout the day or in response to other factors. For example, during later operational hours, vehicles with higher battery levels may be considered unavailable even though the same vehicle with equivalent battery levels may not have been considered unavailable earlier in the day.

Within the Available State 142, a vehicle may be in a subsidiary “Free” state 148, indicating the vehicle is not currently in use by a rider, or in an “In Use” state 150, if the vehicle satisfies the conditions of the Available State 142 (sufficient charge, etc.) but is currently in use by a rider. In various embodiments, vehicles in the Available State 142 that are currently in the subsidiary “Free” State 148 are included in a pool of vehicles considered by the system to be available for use. Vehicles in the Free State 148 within Available State 142 are included and represented in rider-facing mobile app and/or other user interfaces, in various embodiments, as available to be rented.

In various embodiments, the Available State 142 begins when the vehicle is deployed and ends when the vehicle enters the Unavailable State 144. In various embodiments, the Unavailable State 144 begins when a vehicle becomes Unavailable and ends when a charger captures the vehicle.

In various embodiments, upon entering the Unavailable State 144, one or both of the following changes take place in the system: (1) the vehicle no longer appears on the rider user-interface map, and as a result the vehicle can no longer be rented by a rider; and/or (2) the vehicle appears on the charger user-interface map, and as a result, the vehicle can now be captured by chargers.

In the example shown, a dotted arrow from the “In Use” state 150 within the Available State 142 represents an edge case in which a vehicle transitions directly from being in the “In Use” state 150 to be Unavailable State 144, e.g., the user rides the vehicle so long that the battery depletes fully and/or to a level below a minimum threshold to remain in the Available State 142.

In various embodiments, a vehicle in the Unavailable State 144 may be “captured” by a “charger” willing to charge the vehicle for a fee or other consideration. In the example shown in FIG. 1B, a vehicle in the Unavailable State 144 that is captured for charging enters the Charging State 146. In some embodiments, a vehicle is captured for charging by selecting the vehicle in a charger-facing user interface and selecting an option to capture the vehicle for charging. Capture results in the backend database record for the vehicle being updated to indicate it has been captured by the charger, and the user record of the charger being updated to reflect that the vehicle has been captured by the charger.

In the Charging State 146, a charger who has captured the vehicle receives via a charger-facing user interface information indicating where the vehicle is believed to be located. The charger retrieves the vehicle, if it can be located, and charges it using equipment such as charger equipment 104 in the example shown in FIG. 1A. If the vehicle cannot be located by the charger, or is damaged, the charger may submit a report, returning the vehicle to the Unavailable State 144, and in some embodiments triggering responsive action based on the report, such as deploying maintenance or other personnel (e.g., other independent contractors) to locate and/or repair the vehicle.

In various embodiments, the charge state of the vehicle is updated (e.g., continuously, periodically, upon being charged to one or more threshold levels, etc.) and the associated vehicle record is updated to reflect that charge state. Once the vehicle has been charged, the charger deploys the vehicle to a deployment location and the vehicle reenters the Available State 142. In some embodiments, the charger deploys the charged vehicle to a specific location, such as a deployment location reserved by the charger for the purpose. For example, the deployment location may be reserved (e.g., for a time) by the user via a charger-facing user interface. In some embodiments, the charger may be directed to deploy the vehicle to a location associated with a rider and/or a reservation to ride the vehicle.

In some embodiments, different individuals may fulfill different actions during the Charging State, such as capturing, charging, and deploying the vehicle. For example, the Charger who captured the vehicle may not be the same person who physically charges nor deploys the vehicle.

Once the charged vehicle has been deployed and reentered the Available State 142, a transaction is processed to credit (pay) the charger for charging the vehicle.

In various embodiments, the amount that a charger will be paid for charging and/or releasing a vehicle is adjusted in various embodiments based on one or more of:

-   -   1. The amount that the vehicle has been charged relative to the         battery levels at the time of capturing the vehicle     -   2. The location of where the vehicle is deployed     -   3. The time when the vehicle is deployed     -   4. The number of vehicles in a given area and time     -   5. The number of riders in a given area and time

In various other embodiments, one or more other conditions may be considered, such as vehicle operating status, weather conditions, and other factors, that are taken into account when calculating pricing.

In some embodiments in which different individuals may be fulfilling different actions during the Charging State 146, the act of paying each specific charger may take place after each action is fulfilled. For instance, in some embodiments, charger 1 can be paid after capturing the vehicle, charger 2 can be paid after charging the vehicle, and charger 3 can be paid after releasing the vehicle. In other embodiments, the entire Charging State 146 must be completed before paying the charger.

In some embodiments, vehicle maintenance and/or updates may be performed on a vehicle while the vehicle is in a Charging State 146. For example, firmware and/or other software updates and/or configuration updates may be pushed to the vehicle, e.g., via the Charger's mobile device, Wi-Fi, etc. In some embodiments, an additional incentive may be provided to a Charger to perform repairs, tune-ups, maintenance inspections, cosmetic repairs, etc. while a vehicle is in the Charging State 146.

In various embodiments, upon successful deployment of the vehicle after charging, the vehicle enters the Available State 142 and the entire process may be repeated.

FIG. 2A is a flow chart illustrating an embodiment of a process to provide the ability to rent electric vehicles rental on demand. In various embodiments, the process 200 of FIG. 2 is implemented, in whole or in part, by a backend server, such as backend server 112 of FIG. 1A. In some embodiments, all or part of the process 200 may be implemented by instances of a mobile app, each instance running on a mobile device associated with a crowdsourced independent contractor who participates and/or is registered to participate in charging on demand electric vehicles for payment or other consideration.

In the example shown, the geographic location and availability state (e.g., battery charge level, reported as damaged or not, etc.) of vehicles comprising a fleet of on demand electric vehicles is monitored (202). For example, each vehicle may report its location, battery charge level, etc., directly or indirectly, as described above in connection with FIG. 1A.

The location and availability state information is used to provide, e.g., via a mobile user interface, information indicating the location and (optionally) charge level of electric vehicles currently available to be used by a rider (204). For example, each prospective rider may access a map-based mobile user interface to locate an available (and currently free) vehicle in an area of interest to the user. Each vehicle or clump of vehicles may be marked by a pin, icon, or other marker. Hovering on or selecting a given specific vehicle may result in charge level and/or other information being displayed. Vehicle numbers or other identifiers and/or additional information may be displayed, e.g., when the vehicle was last rented and/or used, when the location was last reported, etc.

Information and functionality to unlock, ride, and make payment for riding a vehicle is provided via the mobile or other user interface (206). For example, in some embodiments a user may claim/reserve (e.g., for a limited time) a vehicle to be used by that user. In various embodiments, training on how to ride the vehicle, how to ride safely, local regulations, etc. may be provided via the mobile app.

In various embodiments, a user uses the app to find and select a vehicle to ride. The user is prompted to provide required input, such as to take images of the front and/or back and/or bar codes or other encoded or specific information on the user's driver's license, where required, and/or to read and electronically sign or otherwise acknowledge the provider's terms of service. Additional examples of functionality provided to facilitate vehicle rental include, without limitation, the ability to scan a QRC or other encoded identifier on a structure comprising or mounted on the vehicle.

In various embodiments, a backend server, such as server 112 of FIG. 1A, is configured to receive information from each of a plurality of mobile app instances, each associated with a corresponding device and/or user. The server processes information received from the mobile app instances to enable a rider to ride a specific vehicle. In some embodiments, the server receives an identification of a specific vehicle in the form of a photo of a QRC or other code visible on the specific vehicle. The server verifies the availability state of the vehicle (e.g., not already reserved or rented by another user, sufficient battery charge level, etc.) and if available associates the vehicle with the requesting user for use. In various embodiments, the server unlocks the vehicle for use by the user, e.g., by sending an unlock command directly to the vehicle, if direct communication is available, or through the mobile app instance associated with the request.

In various embodiments, while a vehicle is in use by a rider the rider's mobile device and app may perform ongoing monitoring of the vehicle and the ride. For example, and without limitation, one or more of the following may be monitored and reported to the backend server via the mobile app and device: vehicle charge level; vehicle speed; vehicle location; etc.

FIG. 2B is a flow chart illustrating an embodiment of a process to provide via a user interface information to enable a user to find electric vehicles available for rental on demand. In various embodiments, the process of FIG. 2B is used to implement step 204 of FIG. 2A. In various embodiments, the process of FIG. 2B is implemented, in whole or in part, by a backend server, such as backend server 112 of FIG. 1A. In some embodiments, all or part of the process of FIG. 2B may be implemented, in whole or in part, by instances of a mobile app, each instance running on a mobile device associated with a user registered to rent on demand electric vehicles for use.

In the example shown, current user location and information is received and maintained for each of a plurality of currently running instances of a mobile and/or other app to rent on demand electric vehicles (222). Data to enable a local view of vehicles available for use in an area of interest to the user is sent to respective instances of the app, to be displayed to the respective users (e.g., if/as requested by the user) (224). In various embodiments, vehicle data may be sent to user app instances on request (user opens app, user selects a control to “find” vehicles, etc.) and/or may be pushed proactively to the app, sent to the app when configured to run in the background, etc. Vehicle availability and location information is updated continuously, and refreshed data is sent to each mobile instance to reflect current information (226). In this way, an accurate and dynamically updated view of those vehicles that remain nearby and currently available (free) to be rented is maintained and provided to each user.

FIG. 2C is a flow chart illustrating an embodiment of a process to provide via a user interface information and functionality to use an electric vehicle available for rental. In various embodiments, the process of FIG. 2C is used to implement step 206 of FIG. 2A. In various embodiments, the process of FIG. 2C is implemented, in whole or in part, by a backend server, such as backend server 112 of FIG. 1A. In some embodiments, all or part of the process of FIG. 2C may be implemented, in whole or in part, by instances of a mobile app, each instance running on a mobile device associated with a user registered to rent on demand electric vehicles for use.

In the example shown, upon receiving an indication from a user to ride a vehicle (240), e.g., the user selects a “ride” control in a mobile app or other user interface, verification processing is performed to ensure all user prerequisites to ride have been met (242). For example, in some embodiments, a user may be required to fulfill one or more of the following requirements, if not already met: scan driver's license or other credential; read and indicated electronically acceptance of the provider's terms of use; read and/or acknowledge local regulations and/or safety information; complete app-based tutorial; sufficient funds balance in the user's account; valid credit card on file; etc. Access to vehicle safety and use information, local regulations, etc., is provided via the mobile app (244).

An indication to ride a specific vehicle is received (246). For example, the QRC or other code on a vehicle may have been scanned using the mobile app and device. In various embodiments, in response receiving an indication to ride a specific vehicle the backend server/service marks the vehicle as “in use” and associates the vehicle with the user and/or app instance. In addition, in embodiments in which use is charged based at least in part on ride duration, one or both of the server/service and the app starts a timer.

In some embodiments, a user may be prompted to take a “selfie” or other photo using the mobile app and/or device, e.g., to verify identity and/or to determine by machine learning or other automated processing that the user is wearing helmet or other safety equipment. In some embodiments, an image to verify the user is wearing a helmet may be required in some locations but not others. For example, the image may be required only in areas in which a local jurisdiction requires riders to wear a helmet and/or for providers to verify helmet use.

An indication that the user has ended the user's ride is received (248). In various embodiments, the indication may be received in response to the user selecting a control to “end” the ride. In some embodiments, an indication the ride has ended may be received if the user has not selected the “end” control but the vehicle has not moved for a prescribed amount of time, the user's location (as reported by the mobile app and/or device) has deviated from the location of the vehicle, etc. In some embodiments, if the vehicle has not moved for a prescribed time and/or the user moves more than a threshold distance away from the vehicle, then the mobile app provides a visual and/or audible alert to prompt the user to indicate whether the ride has ended, e.g., “Have you finished your ride?” In various embodiments, the ride duration timer (at server and/or mobile app) is stopped in response to receiving the indication the ride has ended (248).

A transaction to charge the rider for use of the vehicle is processed (250). For example, a credit balance in the user's account may be debited by an amount to be charged for the ride. In some embodiments, rides are charged for on a basis other than ride duration. In various embodiments, prices charged by time or otherwise may be adjusted dynamically, for example in response to fluctuations in demand and/or vehicle availability relative to demand or expected demand in a given area, at a given time of day, etc.

In various embodiments described herein a user interacts with one or both of a service to provide electric vehicles for on demand rental and the vehicles themselves using a mobile app running on a mobile device of the user (e.g., phone, watch, other wearable tech). In various embodiments, techniques disclosed herein may be used without using a mobile app or device. For example, in some embodiments, electric vehicles comprise equipment to interact with riders and to communicate location and state information to a backend server other than via a mobile device. In some embodiments, biometric (face recognition, voice recognition) or other identification processing is performed using image or audio captured by the vehicle itself. A user simply states the user's name (e.g., actual name, user name within the service, etc.) and indicates the user desires and intends to ride a specific vehicle. The vehicle captures and provides to the service biometric (image, audio, etc.) or other information, and upon verification by the server is unlocked by the server and made available for use by the user.

FIG. 3A is a diagram illustrating an embodiment of a user interface to locate and rent on-demand electric vehicles. In various embodiments, the user interface 302 of FIG. 3 is displayed on a mobile device via a mobile app running on the device using data received from a backend server, such as backend server 112 of FIG. 1A. In the example shown, user interface 302 comprises a map-based display in which electric vehicles (e.g., scooters) available to be rented and used are represented by location pin-style icons 304. Each instance of icon 304 may represent one or more vehicles at the indicated location, in various embodiments. In some embodiments, a two-finger squeeze gesture may be used to zoom out and moving two fingers further apart zooms in. In some embodiments, depending on the map scale and number of scooters in each location each icon 304 may represent one or more than one vehicle. As a user zooms in, for example, a group of vehicles represented by a single icon 304 may be disaggregated and each vehicle may come to instead be represented individually, e.g., each by an instance of icon 304.

In the example shown, vehicles are shown (icons 304) in locations relative to streets and/or pathways 306, 308 and landmarks 310, 312, such as buildings, fountains, parks, etc. A ride button 314 may be used to rent a vehicle for use. In some embodiments, a vehicle may be selected in user interface 302 and the ride button 314 selected to reserve the vehicle for use. In some embodiments, selection of the ride button 314 accesses a mobile device camera-based interface via which the user is prompted to use the mobile device to scan a QRC code, bar code, or other information physically displayed on a vehicle to rent the vehicle for use.

A vehicle rented for use in this manner in various embodiments results in the vehicle no longer appearing in corresponding instance of user interface 302 as displayed to other users. Additionally, the vehicle enters the “in use” state on the backend and records to track the user's usage of the vehicle (e.g., time, location, etc.) and to process a transaction to charge the user's credit card or other account for the ride are generated.

In the example shown, user interface 302 includes a menu/option button 316 in the upper right corner. In various embodiments, selection of menu/option button 316 results in a display page with additional controls, options, and/or information being displayed.

FIG. 3B is a diagram illustrating an embodiment of a user interface to locate and rent on-demand electric vehicles. In the example shown, the map-based interface 302 of FIG. 3A has been augmented by adding an overlay 320 indicating a region in which it is not (currently) permitted to ride and/or park a vehicle. In various embodiments, the overlay 320 may be static (e.g., city or other jurisdiction and/or designated portion thereof in which vehicle may not be ridden and/or parked at any time) or dynamic (e.g., building 312 is a school and vehicle may not be operated in the indicated area during school hours, or building 312 is an apartment building for retirees and vehicles may not be operated after dark, etc.). In various embodiments, overlay 320 is generated and displayed in response to user location and area of interest information received at a backend server. If the user is near or uses the map-based interface to explore an area subject to restrictions, a corresponding overlay 320 is generated and rendered as shown in FIG. 3B.

In various embodiments, the map-based interface of FIGS. 3A and 3B includes direction functionality to generate directions and a route to drive or walk from a user's current location to a selected location at which a vehicle indicated by the user is located.

FIG. 4 is a diagram illustrating an embodiment of a user interface to rent an on-demand electric vehicle or charge on-demand electric vehicles. In some embodiments, the options display page 402 of FIG. 4 is displayed upon selection of an additional menu/options button in a rider-facing user interface, such as menu/option button 316 of user interface 302 of FIG. 3 .

In the example shown, display page 402 includes a set of vehicle rider-related options/controls 404. As shown, the additional options/controls include controls to access options/functionality to ride a selected vehicle, to make payments, e.g., for a recently-completed ride or to add to a balance debited to pay for rides; a “free rides” button to learn about incentives and/or promotions that may enable a user to earn a free ride; a “ride history” button to review one's own history of use of on demand vehicles; a “how to ride” button to access video or other tutorials on how to ride on demand electric vehicles correctly, safely, legally, etc.; a “safety” button to learn safety tips and rules; a “help” button to access FAQ, help via a chat interface, etc.; and a “settings” button to change settings, such as screen name, default map view, preferred map program to get a route to a vehicle, payment methods, etc.

In various embodiments, free rides may be earned in a variety of ways, including without limitation one or more of: completing a prescribed number of paid rides; accumulating credits for properly using and/or parking vehicles; a bounty for referring other paid users; performing a service with respect to vehicles used or parked by others, such as standing up a vehicle that has fallen or been knocked over; reporting a damaged vehicle or one suspected of being lost or stolen; and suggesting new areas to stage (park) vehicles for rider use.

In various embodiments, selecting the “X” in the upper right corner (or other control) to close the user interface of FIG. 4 , while in the charger mode as shown, results in display of a map-based user interface, such as the interface of FIGS. 3A and 3B.

FIG. 5 is a flow chart illustrating an embodiment of a process to receive and process an indication to ride an electric vehicle. In various embodiments, the process of FIG. 5 is performed by a backend server, such as backend server 112 of FIG. 1A, based on information received from one or both of vehicles comprising a fleet of on demand electric vehicles and one or more mobile devices associated with a user. In various embodiments, the process of FIG. 5 is performed to implement step 246 of FIG. 2C.

In the example shown, an indication to ride a vehicle is received (502). For example, a user may have provided an indication via a user interface, such as user interface 302 of FIGS. 3A and 3B, to ride a specific vehicle, resulting in an indication to ride the vehicle by that user being sent via the Internet to the backend server. The vehicle is removed from the population of vehicles displayed to riders via a rider-facing user interface (e.g., mobile app) (504). The vehicle and user data records are update to reflect that the vehicle is being used by the user and a ride duration timer is started (506). Upon receiving an indication the ride has ended (508), end of ride processing (e.g., stopping the ride duration timer, returning vehicle to the population available to be rented, processing a payment transaction, etc.) is performed (510).

FIG. 6 is a flow chart illustrating an embodiment of a process to perform end-of-ride processing. In various embodiments, the process of FIG. 6 is performed by a backend server, such as backend server 112 of FIG. 1A, based on information received from one or both of vehicles comprising a fleet of on demand electric vehicles and one or more mobile devices associated with a user. In various embodiments, the process of FIG. 6 is performed to implement step 248 of FIG. 2C, e.g., upon and/or in connection with receiving an indication that a ride has ended.

In the example shown, one or more of the user identification, vehicle identification, user location, and vehicle location are received (602). It is determined whether the release location (where the rider ended the ride) is a valid location to park the vehicle and parking instructions are provided to the rider (604). In some embodiments, if the end of ride location is not a permitted location to park the vehicle, the user is prompted to move the vehicle (e.g., push, ride, ride for free, etc.) to a permitted location, e.g. a nearest permitted location, a preferred location, etc. In various embodiments, the parking instructions may be generic (e.g., parked upright on kickstand, not blocking walkways, doors, crosswalks, fire hydrants or other safety equipment, handicap access, etc.), specific (e.g., information about specific preferred, permitted, and/or prohibited locations at or near the location at which the user ended the ride), or a combination of both. The user is prompted, e.g., via the mobile app, to take a photo of the vehicle as parked (606). The image is received and processed to determine via automated processing (e.g., machine learning-trained classifier) whether the vehicle is parked correctly (e.g., upright, not blocking doors or walkways, etc.) (608). In some embodiments, if it cannot be determined via automated processing of the image whether the vehicle is parked correctly, the image may be sent automatically for human review.

If the image processing and/or review indicate(s) the vehicle is part incorrectly, responsive action is taken (614). For example, the user may be prompted to (more) correctly park the vehicle.

Once the vehicle is determined to have been parked correctly and/or responsive action is taken (610, 614), a payment transaction for the ride is processed and the vehicle is returned to the pool of vehicles available to be rented (612).

FIG. 7 is a diagram illustrating an embodiment of a user interface to provide instructions to properly park a vehicle at a specific location. In some embodiments, the display 700 of FIG. 7 is displayed upon receiving an indication to end a ride at a location for which location-specific parking instructions are available.

In the example shown, display 700 includes a graphical representation 702 of the correct location and manner to park vehicles at the location. The graphical representation may be a drawing, computer graphic, photograph, and/or a mix of one or more of the above. Areas at which vehicles are permitted/desired to be located and the manner of parking them are represented by vehicle images/drawings. Points of reference, obstacles, and other features are represented and areas in which vehicles should not be placed, such as doorways, walkways, bike paths, roadways, etc., are marked with an “X”. A text display area 700 displays information about the location, including in this example the street address and notes regarding how vehicles should and should not be left at the location. A control 706 enables a user to indicate a vehicle has been parked at that location.

For locations for which specific parking instructions are not available, in various embodiments a display page providing generic information about how to properly park a vehicle may be displayed.

FIGS. 8A through 8H illustrate a sequence of mobile app display pages used in various embodiments to instruct a rider with respect to one or more aspects of finding and riding an electric vehicle comprising a fleet of “on demand” vehicles as disclosed herein.

FIG. 8A illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions to find and unlock a vehicle are provided.

FIG. 8B illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instruction to scan a QRC code on the top of the handle bar to unlock a specific vehicle is shown.

FIG. 8C illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions to ride the vehicle safely are provided.

FIG. 8D illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, local rules associated with the specific local jurisdiction in which the user and/or the vehicle are located are displayed.

FIG. 8E illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions on how to positon oneself on the vehicle, in this example by showing how one should place one's feet to stand on the footboard of an electric scooter, are shown.

FIG. 8F illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions on how to start and ride the vehicle are shown.

FIG. 8G illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions on how to use the brake to slow down or stop the vehicle are shown. In this example a hand brake is provided. In various embodiments, a fleet may include a variety of different makes and model of vehicle. Some scooters, for example, may include a heel-operated brake on the back wheel, in addition to a hand brake. In some embodiments, FIGS. 8F and 8G as presented to a given user in connection with a particular vehicle may be adapted dynamically to present a version associated with the braking or other features of vehicles of the type the user has indicated the user intends to ride.

FIG. 8H illustrates an example of mobile app display screen in an embodiment of a mobile app to facilitate on demand rental of electric vehicles. In the example shown, instructions as to areas in which the rider is permitted (bike lanes, etc.) and not permitted (sidewalks) to ride are displayed.

In various embodiments, localization of training (e.g., FIGS. 8A through 8H) is accomplished by determining (e.g., via user mobile device geo-location, vehicle geo-location, etc. a location in which the vehicle is located, and mapping the geo-location to one or more local and/or state jurisdictions, such a municipality and state in which the vehicle and rider are located, adjacent municipalities into which the rider may ride, etc. In some embodiments, a core set of training materials may be augmented by additional screens, images, videos, etc. to communicate information about local requirements, including where the user may ride (street, bike lanes, not on sidewalk, etc., as applicable), permissible speeds, helmet and other local safety requirements, parking restrictions, and/or applicable fines.

In some embodiments, training materials may be adapted to the user's level of experience, as tracked by the app. For example, an experience rider may be required to complete only a refresher segment on basic riding techniques and/or a segment about rules applicable in the particular locale in which the user will be riding.

While in FIGS. 8A through 8H static figures are shown, in some embodiments, training materials may include animated sequences. For example, in some embodiments FIG. 8F may include an animated sequence illustrating a technique to start riding by placing one foot on the footboard and kicking off with the other foot to generate initial movement and then using the thumb-operated throttle to accelerate and ride.

In various embodiments, techniques disclosed herein enable a fleet of shared electric vehicles to be made available for rental without requiring the use or availability of a fixed docking station capable of charging the vehicles.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. 

What is claimed is:
 1. A system, comprising: a communication interface; and a processor coupled to the communication interface and configured to: receive via the communication interface an indication that a ride associated with an electric vehicle has ended; determine an availability state of the electric vehicle based at least on a current battery charge level of the electric vehicle and a dynamic charge threshold; and include information reflecting the availability state of the electric vehicle in a set of geographic location and availability state information of vehicles comprising a fleet of electric vehicles available to be displayed via a user interface based at least in part on the respective availability state of the respective electric vehicles comprising the fleet of electric vehicles.
 2. The system of claim 1, wherein the user interface is a rider user interface.
 3. The system of claim 2, wherein the information reflecting with the availability state of the electric vehicle is included in the rider user interface in response to a determination that the electric vehicle is in an available state.
 4. The system of claim 1, wherein the user interface is a charger user interface.
 5. The system of claim 4, wherein the information reflecting with the availability state of the electric vehicle is included the charger user interface in response to a determination that the electric vehicle is in an unavailable state.
 6. The system of claim 1, wherein the processor is configured to receive via the communication interface monitoring data associated with the electric vehicle.
 7. The system of claim 6, wherein the monitoring data associated with the electric vehicle includes one or more of charge level, speed, and/or location.
 8. The system of claim 1, wherein the processor is configured to determine the availability state of the electric vehicle to be an unavailable state in response to a determination that the current battery charge level is less than the dynamic charge threshold.
 9. The system of claim 1, wherein the processor is configured to determine the availability state of the electric vehicle to be an available state in response to a determination that the current battery charge level is not less than the dynamic charge threshold.
 10. The system of claim 1, wherein the available state of the electric vehicle transitions from an in use state to a free state.
 11. The system of claim 1, wherein the dynamic charge threshold is based on one or more of time, location, or other context factors.
 12. The system of claim 1, wherein the indication that a ride associated with the electric vehicle has ended includes a photo of a code or other identifier associated with the electric vehicle.
 13. The system of claim 1, wherein the availability state of the electric vehicle determined based at least on whether a geo-location of the electric vehicle is inside of operational boundaries.
 14. The system of claim 1, wherein the availability state of the electric vehicle determined based at least on a current time of day.
 15. A method, comprising: receiving an indication that a ride associated with an electric vehicle has ended; determining an availability state of the electric vehicle based at least on a current battery charge level of the electric vehicle and a dynamic charge threshold; and including information reflecting the availability state of the electric vehicle in a set of geographic location and availability state information of vehicles comprising a fleet of electric vehicles available to be displayed via a user interface based at least in part on the respective availability state of the respective electric vehicles comprising the fleet of electric vehicles.
 16. The method of claim 15, wherein the user interface is a rider user interface.
 17. The method of claim 16, wherein the information reflecting with the availability state of the electric vehicle is included in the rider user interface in response to determining that the electric vehicle is in an available state.
 18. The method of claim 15, wherein the user interface is a charger user interface.
 19. The method of claim 18, wherein the charger user interface is provided in response to determining that the electric vehicle is in an unavailable state.
 20. A computer program product embodied in a non-transitory computer-readable medium, comprising computer instructions for: receiving an indication that a ride associated with an electric vehicle has ended; determining an availability state of the electric vehicle based at least on a current battery charge level of the electric vehicle and a dynamic charge threshold; and including information reflecting the availability state of the electric vehicle in a set of geographic location and availability state information of vehicles comprising a fleet of electric vehicles available to be displayed via a user interface based at least in part on the respective availability state of the respective electric vehicles comprising the fleet of electric vehicles. 